You created a custom module that is not functioning as expected on your Integration environment. You would like to debug the code using Xdebug. Xdebug is missing from the output of the command php -m.
What are two ways to load the Xdebug module? (Choose two.)
Answer : AC
You are debugging an issue with an extension that only occurs in Production. The extension writes relevant information using the debug log level.
However, that specific information is not getting written to the logs on Production.
How do you fix this?
Answer : D
Reference:
https://devdocs.magento.com/guides/v2.3/config-guide/cli/logging.html
You cloned the Integration branch to your local environment and imported the database dump from Integration. You performed composer install and bin/ magento setup:install.
While placing an order using PayPal Express, the following error occurs:
PayPal gateway has rejected request. Security header is not valid (#10002: Security error).
What is the cause of this error?
Answer : C
You want to exclude some themes from static assets generation only for integration environments. You are trying to choose where to set the
SCD_EXCLUDE_THEMES variable in the .magento.env.yaml file or in the Project Web UI.
What prevents the usage of the .magento.env.yaml file?
Answer : C
You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension-fix.patch.
Before committing the patch to the repository you want to test it locally.
How do you test a patch in a clean working copy?
Answer : B
Reference:
https://devdocs.magento.com/cloud/project/project-patch.html
You need to test a data-related issue occurring on your Production environment. You replicate the data to your staging environment utilizing the Synchronization tool. When you access your staging environment, you are redirected to your Production environment. Your project is on the Starter plan.
How do you prevent the redirect?
Answer : C
You upgraded an integration branch in your Magento Commerce Cloud project, but received an error during the deploy phase.
What are the two ways to review details about the deployment? (Choose two.)
Answer : AC
Your company decided to move a Magento store to a subdomain https://shop.company.com/ and redirect traffic from the old URL https:// company.com/ to the new one. Your company is using the Starter plan.
How do you implement the redirect?
Answer : D
Reference:
https://devdocs.magento.com/cloud/project/project-routes-more-redir.html
You built a custom command that runs during the build phase, but it is not generating files properly. Magento Support provided a patch that you added to the project.
What must you do to ensure this command runs after the patch has been applied?
Answer : A
Reference:
https://support.magento.com/hc/en-us/articles/360031098011-Deployment-fails-with-Error-building-project-The-build-hook-failed-with-status-code-1-
You add a new Composer dependency utilizing composer require. After testing composer install locally, you add the Composer lock and json files and perform a deployment. The build phase fails as Composer is unable to resolve the dependencies.
Why did this happen?
Answer : A
You want to move static content deploy to the build phase of deployments.
Which two actions do you take? (Choose two.)
Answer : BD
You need to install a third party extension which is provided in a tar archive. It expands to a folder structure in app/code/MyCompany/MyModule.
Which action do you take to install the extension?
Answer : C
A merchant states the downtime during the deployment phase is too long. After analysis, it is determined the static content deployment is the longest process.
Static content needs to be available immediately after deployment.
How can the static content deployment time be reduced?
Answer : A
Reference:
https://support.magento.com/hc/en-us/articles/115003169574-Reduce-deployment-downtime-on-Magento-Cloud-with-Configuration-
Managementsachin -
You need to directly access the database that belongs to your Integration environment from your local environment.
How do you achieve this?
Answer : C
A custom module that adds a new console command for bin/magento has just been built. Deploying this to the Production environment on your Pro plan site causes the build phase to fail.
You find this occurs when you inject certain Magento core classes in your console command class. The command works on your local environment.
Why does this occur?
Answer : A
Have any questions or issues ? Please dont hesitate to contact us